View AT24RF08C_1004122.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1 features ? dual-port nonvolatile memory - rfid and serial interfaces two-wire serial interface: ? compatible with a standard at24c08 serial eeprom ? programmable access protection to limit reads or writes from either port ? lock/unlock function, coil connection detection rfid interface: ? 125 khz carrier frequency for long range access ? 2-wire connection to external coil antenna and tuning capacitor ? multi-tag management to handle several tags in the field at once ? 12 rfid commands for tag control and memory read/write ? id write and lock from rfid port ? ultra low power single bit write - 25 a highly-reliable eeprom memory ? 8k bits (1k bytes), organized as 8 blocks of 128 bytes each ? 16-byte page write, 10 ms write time ? 10 years retention, 100k write cycle endurance -40 c to +85 c operation, 2.4v to 5.5v supply, 8-lead jedec soic package description the AT24RF08C functions as a dual access eeprom, with both a wired serial port and a wireless rfid port used to access the memory. access permissions are set from the serial interface side to isolate blocks of memory from improper access. the rfid interface can be powered solely from the attached coil permitting remote reads and writes of the device when vcc is not applied. block diagram pin configurations pin name function l1 coil connection l2 coil connection prot protection input gnd ground sda serial data,open drain i/o scl serial clock input wp write protect input vcc supply: 2.4v - 5.5v asset identification eeprom AT24RF08C rev. 1072e ? 09/99 8-pin soic 1 2 3 4 8 7 6 5 l1 l2 prot gnd vcc wp scl sda
AT24RF08C 2 general overview the AT24RF08C is intended to be pin compatible with standard serial eeprom devices except for pins 1, 2 and 3, which are address pins in the standard part. other exceptions to the at24c08 serial eeprom data sheet are noted in the ? serial eeprom exceptions ? section later in this document. connection of an external coil antenna and optional tuning capacitor, normally via a two conductor wire, is all that is required to complete the rfid hardware requirements. throughout this document, the term ? reader ? is defined as the base station that communicates with the chip. under all expected conditions, it actually serves as both a reader and writer. the term ? tag ? is used to indicate the chip when operating as an rfid transponder with the coil attached. all bits are sent to or read from the device, most significant bit first, in a manner consistent with the at24c08 serial eeprom. the bit fields in this document are correspondingly listed with the msb on the left and the lsb on the right. eeprom organization the eeprom memory is broken up into 8 blocks of 1k bits (128 bytes) each. within each block, the memory is physically organized into 8 pages of 128 bits (16 bytes) each. in some instances, accesses take place on a 32-bit (4 byte) word basis. in addition to these 8k bits, there are two more 128-bit pages that are used to store the access protection and id information. there are a total of 8448 bits of eeprom memory available on the AT24RF08C. access protection (both read and write) is organized on a block basis for blocks 1 through 7 and on a page and block basis for block 0. protection information for these blocks and pages is stored in one of the additional pages of eeprom memory that is addressed separately from the main data storage array. see ? access protection ? on page 3 for more details. the id value (see ? id configuration ? on page 7) is located in the id page of the eeprom, the second of the additional 16 byte pages. writes from the serial port may include from one to 16 bytes at a time, depending on the protocol followed by the bus master. accesses to the eeprom from the rfid port are on either a word (32 bits) or page (128 bits) basis only. all page accesses must be properly aligned to the internal eeprom page. the eeprom memory offers an endurance of 100,000 write cycles per byte, with 10 year data retention. writes to the eeprom and tamper bit take less than 10 ms to complete. completion time for writes initiated from the rfid port are different depending on the situation. when external power is supplied to the chip through the vcc pin, writes to the eeprom and tamper bit take less than 11.8 ms when measured from the last modulation edge before the write to the first after the write. when powered from the coil pins at 125 khz, the eeprom write time will be 5.8 ms and the tamper write time will be 7.9 ms. after manufacturing, all eeprom bits except in the device revision byte (see ? access protection ? page 5) will be set to a value of 1 and the tamper bit will be set to 0. device access the third device address bit in the two wire protocol that is usually matched to a 2 (pin 3) on a standard at24c08 serial eeprom is internally connected high, so device addresses a8 through af (hex) are used to access the memory on the chip. the general command encoding used by the serial port for eeprom accesses is shown below in device access examples, where b 2-0 is the block number, p 2-0 is the page number within the block and a 3-0 is the byte address within the page. bits denoted as ? x ? are ignored by the device. the prot pin is used as a power good signal. when this pin is low, the serial port is held in reset and all sticky bits are set to one. when high, activity on the serial bus is permitted. device access examples for write operations: 1 0 1 0 1 b 2 b 1 0b 0 p 2 p 1 p 0 a 3 a 2 a 1 a 0 d 7 d 6 d 5 d 4 d 3 d 2 d 1 d 0 ? for read operations: 1 0 1 0 1 x x 1 d 7 d 6 d 5 d 4 d 3 d 2 d 1 d 0 ?
AT24RF08C 3 access protection all access protection bits are stored on a separate page of the eeprom that is not accessed using the normal commands of an at24c08 memory. see the ? access protection page ? section on page 5, for more detail on this information. the rfid access (rf) fields in the access protection page determines whether or not the corresponding block within the memory can be read or written via the rfid interface. if an illegal command is attempted, the command will be aborted. the msb, if clear, prohibits all accesses from the rfid port, and the lsb if clear prohibits writes from the rfid port. the fields are stored in the eeprom and organized as follows: the protection bits (pb) fields in the access protection page determine what type of accesses will be permitted via the serial port for each of the blocks on the chip. if an illegal access is attempted, the command will be nack ? ed. the msb, if clear, prohibits all accesses to the block, and the lsb if clear prohibits writes. the fields are stored in the eeprom and are organized as follows: the tamper write (tw) bits within the access protection page control whether or not a write will be permitted into the corresponding block of memory when the tamper bit is set. if the tamper bit is a 1 and the tw bit is a 0, then writes to that block from the rfid port are not permitted. in all other cases, writes are permitted according to the rf field value for that block. the value of this bit does not affect accesses from the serial port. accessed within the access protection page is an individual cmos sticky bit (sb) for each of the 8 blocks on the device. when the value of the sticky bit is 0, the protection bits (pb) for the corresponding block may not be changed via the software. these bits are all set to one when power is initially applied or when the prot pin is low. these sticky bits may be written only to a 0 via the serial interface using the standard serial write operations. reading the sticky bits does not affect their state. because access permissions are set individually for each of the blocks, all reads via the serial port will only read bytes within the block that was specified when the current address was latched into the device (with a write command). the block address bits (b 2 or b 1 ) that are sent with the write command are ignored on a read command. after the read of the last byte within a block, the internal serial address wraps around to point at the beginning of that block. after the write of the last byte in a page, the internal address is wrapped around to point to the beginning of that page. if more than 16 bytes are sent to the device with a write command, the data written to any overlapping bytes will be corrupted. if the wp pin is high, all write operations are prohibited from the serial port, although write commands may be used to set the address for a subsequent read command. block 0 write protection bits the AT24RF08C provides a mechanism to divide block 0 into eight 128-bit (16 byte) pages that can be individually protected against writes from either port. these eight write protection (wp) bits are stored within a byte of the access protection page and are organized such that the lsb protects the first 128 bits and so on. if a bit in this byte is set to a one and the pb 0 field is set to 11, then writes are permitted on the page corresponding to the wp bit. if the wp bit is set to a 0 or the pb 0 is any value other than 11, then writes are not permitted in that page. the write protection hierarchy for serial accesses is shown on the following page. in this drawing the bits within the boxes to the left of the arrows are the only thing that determine whether or not the bit in the box to the right of the arrow can be written. read access control is not shown in this diagram. addresses listed in this diagram are for the serial port assuming that the r/w bit in the command byte is set to 0. rfid access fields (rf) msb lsb function 0 0 no accesses permitted from rfid port 0 1 no accesses permitted from rfid port 1 0 reads only from the rfid port 1 1 no restrictions for rfid accesses protection bits (pb) msb lsb function 0 0 no accesses permitted in the block 0 1 no accesses permitted in the block 1 0 read only, writes cause a nack 11 read/write - no access constraints for data within this block
AT24RF08C 4 for example, when sb1 is a 1, the pb1 field can be written to any value by the system. when the pb1 field is 11, block 1 can be written by the system. note that the state of the sb1 bit does not affect whether or not block 1 can be written. there is no individual page write protection for any other block other than block 0 within the device. within the remaining blocks on the chip, access permissions are con- trolled on a block basis (pb or rf bits) or full chip basis (wp pin) only. write protection flow eeprom tamper latch there is an additional eeprom tamper latch that can be set from the rfid port and reset from the serial port of the device. resetting this bit from the serial port takes less than 10 ms. setting of this bit from the rfid side when powered from l1/l2, takes about 7.9 ms but requires less than 30 a of current. see ? rfid command ? on page 8. access to this tamper bit from the serial interface is via the lsb of the tamper byte of the access protection page. see ? access protection page ? below. the bit can only be set to 0 via the serial port. attempts to write it to a value of one are ignored.
AT24RF08C 5 access protection page the serial port may be used to read and write the access protection page (app) and id page using device access codes of b8 and b9 (hex) instead of the normal value of a8 through af (hex) that are used to access the rest of the eeprom memory. the second byte of write commands (the word address) should be in the range of 00 through 0f (hex) for the app page and 10 through 1f (hex) for the id page. this coding is shown below. reads and writes to these two pages may take place on a single byte basis only. multi-byte operations will be nack ? ed. as an example, the bit encoding for a single byte read and write command are shown below. the AT24RF08C will acknowledge all device addresses of b8 or b9 (hex). if the most significant three bits of the word address are not all 0 (indicating an address outside the access protection and id pages), the chip will nack the access. bytes 0 through 7 of the app contain 8 identical sets of access control fields (pbx, rfx, twx and sbx) for each of the eight blocks of memory on the chip, which operate according to the table listed in the access protection sec- tion above. when the sticky bit in one of these bytes is set, that byte can be written by the system. once a sticky bit is reset (written to zero) by the software, the byte containing it can no longer be modified by the software until the next power cycle. these bytes can always be read by the sys- tem. byte 8 contains another pb field (pb ap ) as bits 0 and 1 and an additional sticky bit (sb ap ) as bit 7. the value of the pb ap bits controls read and write access to the last 7 bytes (#9-15) of the app and all 16 bytes of the id page according to the encoding listed in the ? access protection ? section above. the value of the pb ap bits can only be changed (via writes from the serial port) when sb ap is high. this byte can always be read by the system. bits 0 through 6 of this byte are stored in eeprom memory and do not change when the power is cycled or the prot pin changes state. byte 9 contains the 8 block 0 write protection bits (wp) for each page within block 0. byte 10 is the tamper byte, and the lsb of this byte can be used to determine if the ? set tamper ? command had been executed from the rfid port. this bit can be reset in software via the serial port by writing a 0 to it. byte 10 also contains the coil detection control. this feature is intended to permit the system to determine if a coil is connected to the pins. it works by driving a small current through the coil pins and determining if there is a low resistance between them. the coil resistance must be less than r coil for the coil to be properly detected. to enable this, the detect enable (de) bit should be set to a 1. after a delay of at least 200 s, the detect coil (dc) bit is then read and a ? 1 ? indicates that a coil is present. note that the rfid interface may not function properly when the de bit is set to a 1, and so the software should ensure that it is always written to a 0 when the coil detection sequence has completed. the de bit is automatically reset to a 0 upon power-up or when prot is held low, but is not timed out internally by the device. when the de bit is low, the value of the dc bit will default to a high state. this does not indicate the presence of a coil, as the state of the dc bit is only valid when the de bit is high. bytes 11 through 14 are currently reserved and should not be used by the system. byte 14 may not be written by the device (via either interface) at any time. access protection page examples for write operations: 1 0 1 1 1 0 0 0 0 0 0 a 4 a 3 a 2 a 1 a 0 d 7 d 6 d 5 d 4 d 3 d 2 d 1 d 0 for read operations: 1 0 1 1 1 0 0 1 d 7 d 6 d 5 d 4 d 3 d 2 d 1 d 0
AT24RF08C 6 byte 15 contains device revision information. it is set at the wafer production facility and cannot be changed in the field, so any write to this byte will be ignored. the least significant three bits are used to show the production revision for the part. the next three bits are used to denote the option set chosen and the most significant two bits describe the basic functionality of the device. the value of this byte is 01 001 001, or 49 (hex). the memory map for the access protection page is shown in the table below. in this table, an x means that the value is a don ? t care upon writing and that it is undefined upon reading. the rf and pb fields are all two bits wide, and the device revision field is 8 bits wide. all other fields are one bit wide. with the exception of the 9 sticky bits (sb) and the two coil detect bits (de and dc), all bits within the access protection page are stored in eeprom memory. their state does not change if power is removed or when the prot pin is held low. the following page of memory (accessed with a 4 = 1) contains the id field transmitted by the device from the rfid port. bytes within it are accessed via a device address byte of b8 / b9 (write / read, hex) and a byte address of 10 through 1f (hex). reading and writing to this id page is permitted when pb ap is 11. the least significant three bits of the first byte should vary to optimize multiple tag performance. the msb of the last byte of the id page is a lock bit that controls writes to the id page from the rfid port. if this bit is a 0, writes to this page from the rfid part are locked out (prohibited). this bit does not affect operation from the serial side, and can be read and written to either state normally from the serial port. the id page can always be read from the rfid port. please note that neither the rf fields nor the tw bits protect the id page against writes from the rfid port. unless the id value is locked using the id lock bit, the user can write to the id page regardless of the state of any access control bits. other than setting the tamper bit via the rfid commands or reading the id field when so directed, there is no way for the rfid port to directly read or write the access protection page. app memory map address bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0sb 0 tw 0 rf 0 xx pb 0 1sb 1 tw 1 rf 1 xx pb 1 2sb 2 tw 2 rf 2 xx pb 2 3sb 3 tw 3 rf 3 xx pb 3 4sb 4 tw 4 rf 4 xx pb 4 5sb 5 tw 5 rf 5 xx pb 5 6sb 6 tw 6 rf 6 xx pb 6 7sb 7 tw 7 rf 7 xx pb 7 8sb ap xxxxx pb ap 9 wp7 wp6 wp5 wp4 wp3 wp2 wp1 wp0 10 de dc x x x x x tamper 11 reserved 12 reserved 13 reserved 14 reserved 15 device revision
AT24RF08C 7 serial eeprom exceptions in general, the two-wire serial interface on the AT24RF08C functions identically to the at24c08. the following exceptions exist, as noted elsewhere within this document. pins 1, 2 and 3 have a different usage. access to various blocks may be restricted via the access protection circuitry. the two block address bits (b2 and b1) in the command byte are ignored with all read commands. they are set only via the write command. multi-byte reads do not cross block boundaries, but instead wrap to the beginning of the block. operation of the serial bus at 400 khz is not guaranteed. maximum operating voltage is 5.5v, maximum operating temperature is 85 c. the serial port will be reset whenever the prot pin is low. if a multi byte read is in progress when an rfid write starts, all data will be read as all 1s. under some circumstances, subsequent bytes within a multi-byte read may have their data returned as all 1s to the serial port if a read is simultaneously requested from the rfid port. if more than 16 bytes are written to the eeprom with a page write, overlapping bytes will have their values corrupted. if v cc is 0v, the device draws current on the sda, scl, wp and prot pins when they are brought above 0v. rfid port operation the AT24RF08C includes a powerful and flexible rfid communications port that permits moving data into or out of the device through a simple coil antenna. features include automatic serial number transmission as well as commands for explicit reads and writes to specified locations within the eeprom. special capability has been added to permit a tag to be individually identified and selected when it is within the field at the same time as the other tags. the general strategy for implementing multiple tags within the field is as follows: upon power-up, the tag waits a random period of time and then transmits, as a header, a fixed pattern that occupies four bit times. the value of each half-bit time is fixed at the pattern 01 11 11 10. (this is interpreted as one half-bit time with no modulation, 3-bit times of modulation and another half-bit time of no modulation). within the following listening window, the tag must receive an acknowledge pulse from the reader. see the ? listening window ? section for restrictions on this transmission. if the tag does not see an acknowledge pulse during the specific time within the listening window, but sees an acknowledge pulse or command issued by the reader to another tag, it goes into an infinite listening window until the other tag is complete with its transaction. if the tag does not see an acknowledge pulse or command from the reader at any time, it will wait for a random length of time before transmitting its four bit header again. if it does receive this acknowledge pulse during the specific time, then it will continuously transmit its complete id (defined below) with a three bit listening window between frames, until a command is received from the reader. after the id has been properly received by the reader, the tag will expect to receive a command from the reader during the three bit listening window between id frames. one possible command is to set the quiet bit, causing the device to remain idle until the next power down or global command. remaining tags will then follow the same procedure until each has its quiet bit set. id configuration after the chip ? s header field has been acknowledged, the chip will transmit as its id number, the first 12 eeprom bytes in the id page, starting with byte 0. this transmission will start 1664 ms after the end of the header transmission. see ? rfid acknowledge timing ? on page 16. this id transmission will be preceded by a single start bit that has a logical value of 1, and terminated by a single stop bit that has a logical value of ? 0 ? . these start and stop bits bracket each page or block of data transmitted by the device as a result of a read or write command. after transmission of the id frame, the device will delay transmission during a 3 bit listening window to listen for a command to be initiated before repeating the id transmission again. commands sent to selected tags must be initiated during the t cdm1 interval within this listening window, as per the ? listening window ? section on page 9. if a write is taking place to the eeprom from the serial port, the device will transmit to the reader a logical 0 in place of the id value until that write completes. if a write from the serial port has started before the command is issued by the reader, then the command will be aborted and the 4 bit header sent. if a serial port write starts after a read command has commenced, then a 0 will be transmitted to the reader during the time that the eeprom is busy with the write. in some cases, reads from the serial port will also cause data to temporarily be read as 0 ? s.
AT24RF08C 8 non eeprom aspects of the rfid port operation, including setting of the tamper bit, will take place normally regardless of the actions on the serial port. operation of the rfid port does not depend on the state of any pin or the state of any sticky bits, as power to the chip may not be applied via the vcc pin when such operations are taking place. rfid commands the explicit commands implemented in this tag permit the reader/writer to directly access individual areas within the memory array and are encoded as follows. in all cases below, ? c 1 c 0 ? represents the two bit error detection field (see ? error detection ? on page 11) for the command that is used to prevent improper command execution. for all commands, the first three bits transmitted (b 10 - b 8 ) form a three bit unique command initiation pattern (cip) that allows the transponder to be synchronized with the reader / writer. the middle bit of this pattern (signified by ? e ? for error in the table below) is an entire bit time of no modulation, which is a manchester error. the entire command initiation pattern consists of ? bit time of modulation followed by two bit times of no modulation followed by ? bit time of modulation. the three global commands may be sent to selected chips during the second bit of any three bit listening window or to unselected , chips in the init state or quiet chips at any time. in general, they operate upon all tags within the field, however, if a chip is currently transmitting data to the reader or waiting for an ack pulse, it will not be able to recognize these commands. for the read and write commands, the data corresponding to the accessed word or page is repeatedly transmitted back to the reader by the device, after the command has completed. this permits a verify function for the write operation and a repetition check for the read data. after the last bit of a read command is sent, there is a delay of 136 cycles before the first read data bit is transmitted by the chip. after a write command, there is a delay of t wd before the written data is transmitted back to the reader. there should be no modulation of the carrier by the reader during these delays. between each 32 or 128 bits of data transmitted, there is a 3-bit listening window to synchronize the reader and/or to permit the reader to issue a new command to the device. see ? listening window structure ? on page 9. there is no delay interval between the transmission of the write commands and the data that is to be written. immediately after the last bit of the command (c 0 ), the most significant bit of the data should be sent to the device without any interruption. there is no retransmission of the data after the global write word command, since multiple tags are expected to be able to have executed this command at the same time. to verify proper operation of this command, each tag must be individually selected and the word read explicitly using the read word command. command encoding b 10 b 9 b 8 b 7 b 6 b 5 b 4 b 3 b 2 b 1 b 0 meaning 0e1b 2 b 1 b 0 000c 1 c 0 set block address latch (bl) to b 0e1p 2 p 1 p 0 010c 1 c 0 set page address latch (pl) to p 0e1111100c 1 c 0 set block address latch (bl) to id block 0e1p 2 p 1 p 0 101c 1 c 0 write page p in block bl (followed by 128 bits of data) 0e1p 2 p 1 p 0 001c 1 c 0 read page p in block bl (followed by 128 bits of data) 0e1w 1 w 0 0111c 1 c 0 write word w, page pl, block bl (32 bits of data) 0e1w 1 w 0 0011c 1 c 0 read word w, page pl, block bl (32 bits of data) 0e1010110c 1 c 0 disable chip until power down (set quiet bit) 0e1101110c 1 c 0 global reset quiet bit 0e1110110c 1 c 0 set eeprom tamper latch (selected tag only) 0e1100110c 1 c 0 global set eeprom tamper latch 0e1w 1 w 0 1111c 1 c 0 global write word w, page 1, block 0 (32 bits of data)
AT24RF08C 9 both the bl and pl registers used in the read and write commands to determine the address are set to 0 upon power-up. the pl value is automatically set to the transmit- ted value when the write page and/or read page commands are executed. the ? set bl to id ? command permits the id page (page 1) to be written from the rfid port if the lock bit is set to a one. this lock bit is the 121st bit sent as part of a write page command or the 25th bit sent as part of a write word 3 command. the first 96 bits of this page are the id bits which are transmitted by the chip in the same order as they are written. the pl register value is ignored when the bl points to the id page. also, the page number is ignored on page write commands. listening window structure after any header, id or data element is read from the device (for any reason) the chip delays further transmissions for a period of time to determine if the reader intends to communicate with the tag. the length of the various delays and the actions that the device takes during this delay depends on the current state of the device and/or any command issued by the reader. in general, the tag expects to see communications from the reader start between the middle of the first bit time and the end of the second time (256 s to 1024 s) after the end of the previous communication. the beginning of the first and the entire third write bit times are ignored in order to prevent the tag from erroneously seeing its own modulation as incoming from the reader. specific timing requirements for these communications are shown in the rfid acknowledge timing diagram and the rfid command/data timing diagram on page 16. there are four states possible for tags that are sufficiently in the field for the internal voltage to be above the reset level. they are listed below and shown in bold throughout this document. init upon power up, and after execution of the global reset quiet bit command, all chips are in this state. chips that do not have their quiet bit set also go into this state after the execution of a disable/set quiet command. while in this state, chips delay a random length of time and then transmit their 4-bit header. tags in this state honor all global commands except those that start during the period in which they are transmitting their header and during the first 512 s of the listening window. they transition to unselected after global command execution, other than global reset quiet which stays in init. selected if the reader issues an acknowledge pulse to a tag in the init state during the second write bit time after the header is transmitted, then the tag is selected and it will repeatedly transmit its id until the reader sends a command to the tag. the tag remains selected through the entire sequence of id transmission and subsequent command execution unless there is a fault of some kind. unselected if a tag in the init state senses modulation interval greater than 32 s in length during any bit time other than the second then it moves into the unselected state, and remains that way until it sees a disable chip command. unselected tags also honor the three global commands while they are ? waiting ? . all other commands are ignored. quiet when in the quiet state, the chip does not activate its modulation resistor at any time. only the three global commands will be honored by the chip. all other commands are ignored. the following paragraphs describe five kinds of delays that are possible. random the chip delays a pseudo random length of time. the length of this delay sequences through the following number of read bit times (128 s each): 64, 48, 24, 32, 56, 40 and 72. the starting point among this list is based on the first three bits of byte 0 of the id page within the eeprom. if these bits are 111, then the sequence above will be preceded by a 16-bit delay. the minimum and maximum delays are 2048 s and 9216 s, respectively. three bit the device waits for three write bit times and then one read bit time (for a total of 1664 s) before retransmitting the data that was just transmitted. during the t cdm1 interval, the reader may issue a command to the chip. see ? rfid command/data timing ? on page 16. long after certain commands, selected chips wait indefinitely for the next command from the reader. this command should start during the t cdm1 interval after the end of the command transmission. infinite unselected chips wait in this state for any of the three global commands or the disable chip command. if no legal command transmission ever occurs, then the device will stay in this delay loop for as long as power is applied from the rfid port.
AT24RF08C 10 quiet similar to ? infinite ? except that only the global commands are honored. if the operation of the system includes only multi tag id transmission along with the use of the global set tamper command, it is useful to note that the global set tamper command should be sent to every device before the disable chip/set quiet command is sent to the selected tag. since tags in the init state transition to unselected with a global command, the disable chip/set quiet will automatically bring them back to init to complete the multi- tag discrimination procedure. in some cases, it is possible for multiple tags to be selected inadvertently, or for tags to be in a state that the reader does not expect. normally, a global reset quiet command may be issued to reset all tags, but this will be ignored by a device while it is transmitting its id. issuing this command three times in succession will ensure that any rogue chips go back to the init state. the table below combines the two lists above to show what delay is used, depending on the current state of the chip and the command that is issued by the reader. in the state transition diagram, shown on the next page, the same information is shown graphically in a state diagram for the chip. note: 1. after the data for a write is sent to the device, there will be a delay of t wd or t twd . the written data will be read back to the reader and then the ? three bit ? window will occur. during this delay, the device ignores all data sent to it. delay length for commands command selected unselected quiet set block address latch long infinite quiet set page address latch long infinite quiet write page p in block bl three (1) infinite quiet read page p in block bl three infinite quiet write word w, page pl three (1) infinite quiet read word w, page pl three infinite quiet global write word w long infinite quiet set eeprom tamper latch long (1) infinite quiet global set tamper latch long infinite quiet disable chip/set quiet bit quiet random quiet global reset quiet bit random random random
AT24RF08C 11 state transition diagram error detection in order to increase the reliability of data transmissions to the AT24RF08C, an error detection field must be sent by the reader after the command word and each byte of data sent from the reader. this field is computed as the number of bits turned on in the byte modulo 4. in order to prevent the checksum from matching the data for repeated 0 ? s or 1 ? s, the least significant bit (c 0 ) is then inverted. for the command word, only the 6 varying bits (b 7 - b 2 ) are used to compute the checksum. there are several levels of error detection utilized to prevent improper execution of a command. if the command encoding is illegal, or the checksum is wrong, or if there is a manchester error in either the command or data or if there is a protection failure, then the entire command will be aborted. once in that state, the device will wait a random period of time before transmitting the header sequence. on both id and data sent from the chip, the chip generates and transmits a single parity bit after each 8 data bits are sent to the reader. internally, parity is computed in such a way that the number of 1s in each 9 bit group is even. the start and stop bits are not included in the parity generation. no parity is generated on the 4-bit header. it is expected that the reader may either embed additional error detection bits within the data and/or read the data two or more times to reduce the rate of bit errors. init wait for no mod. write in progress read page/word write page/word set bl / pl set tamper all globals selected long listen write done invalid command/data invalid command/data ack in window mod outside ack window global reset quiet / set quiet set quiet set quiet global reset quiet no mod quiet global write word global set tamper other modulation ignored unselected global write word global set tamper other modulation ignored global reset quiet global reset quiet selected 3 bit listen read page/word write page/word set bl / pl set tamper all globals commands listed in italics
AT24RF08C 12 transmission: encoding and modulation data is transmitted to the reader using resistive modulation which is implemented as a variable modulation resistor switched across the coil pins. data from the eeprom is encoded using miller encoding before driving the modulation resistor. if the output of the miller encoder is a 1, then the modulator resistor is turned on and vice versa. in miller encoding, if the data state is a 1, there is a transition in the middle of the bit time. if the data state is a 0, there is no transition if the next data bit is a 1 or a transition at the end of the bit time if the next data state is a 0. each data or id group transmitted (other than the header) includes a start bit which has a value of 1. this is always interpreted as a transition from modulator-off to modulator- on in the middle of the start bit time, preventing a half-bit time modulation pulse. data is transmitted from the chip at a rate of one bit (into the encoder) for each 16 carrier cycles. after the data has been transmitted, a single stop bit having the value of 0 will be transmitted. depending on the state of the last parity bit, this will be either one cycle of modulation or one cycle of no modulation. the following diagram shows the functional signal waveforms for data transmission. data transmission
AT24RF08C 13 reception: decoding and demodulation for data received by the chip, a drop in amplitude is interpreted as a low state, while an increase in amplitude indicates a high state. the output of this demodulator is inverted and then decoded using manchester decoding before being interpreted as commands or data. in manchester decoding, (sometimes called biphase), there is a transition in the middle of each bit time. if this is a high-to-low, the data state is a 0, and if low-to-high a 1. data is received by the chip at a rate of one bit (out of the decoder) for each 64 carrier cycles. each command must be preceded by a command initiation pattern (cip). the receiver uses the leading edge of the first modulation change of the cip to automatically synchronize to the incoming data stream. that edge must occur during the t cmd1 interval after the end of the last bit previously transmitted or received by the chip. this edge is used to start a bit clock against which all remaining edges are timed. the remaining two edges within the cip occur during the middle of the first and third bit times of the command. they must occur within specific time intervals (t cmd2 ) from the beginning of the bit time, and their specific time locations (within the bit times) are used to synchronize with subsequent edges (t cmd3 ) occurring in the same direction (rising or falling). edges that correspond to manchester changes at the beginning/end of a bit are not explicitly used by the chip. if no edges of the cip fall within the t cmd1 window after a read of some sort (including id read), the chip will retransmit the data that was previously read. the following diagram shows functional waveforms for data reception. data reception
AT24RF08C 14 voltage levels the chip includes a voltage reference to ensure that command initiated reads and writes from the rfid port are only performed when the power supply voltage on the chip is above the level (vcoil2) at which eeprom reads and writes can be guaranteed. if an eeprom read or write is attempted when the voltage is too low, the command will be aborted. below the vcoil2 level, but above a minimal operating voltage level of vcoil1, header and id reads are permitted. in addition, the two tamper latch commands and the two quiet bit commands may also be executed at lower voltages. because the eeprom data may not be read correctly at this voltage, the id field must contain some error detection information stored within it. proper setting of the tamper bit feature is guaranteed only if v coil is above 3.7v for greater than 6.1 ms, but under typical conditions, the circuit will operate over a much wider range. when power is removed from the serial interface side (vcc pin), the rfid operation will be momentarily reset while the internal circuitry switches the internal power supply to the rfid bridge. when the voltage on the vcc pin is held to above 0.6v but less than 2.4v (both nominal), all read and write commands from the rfid port may be inhibited. id transmission and tamper bit commands may be executed, although their operation may not be correct. absolute maximum ratings coil voltage (peak-to-peak) maximum.............................................................................24v *notice: stresses beyond those listed under ? absolute maximum ratings ? may cause permanent damage to the device. this is a stress rating only and functional operation of the device at these or any other conditions beyond those indicated in the operational sections of this specification is not implied. exposure to absolute maximum ratings conditions for extended periods may affect device reliability. operating junction temperature...........................-40 to +85 c storage temperature (without bias)...................-55 to +125 c voltage on v cc with respect to ground............................................................6.0v voltage on sda, scl, prot and wp............-0.1 to v cc +0.3v
AT24RF08C 15 parametric specifications unless otherwise noted, all specifications are over the temperature range of -40 c to +85 c . notes: 1. some parametric limits are design targets that may be refined on the basis of production history. 2. coil voltages are measured with respect to the on chip ground, which is centered on the ac voltage from the coil. peak-to-peak coil voltages would be double those listed above. transmit test circuit test waveform rfid dc specifications (1) at f coil = 125 khz, v cc (serial) = 0v. name min typ max units notes p coil 160 mw maximum power dissipation from l1/l2, peak v coil1 1.6 2.2 3.1 v coil voltage (2) for id transmission v coil2 2.7 3.0 3.7 coil voltage (2) for eeprom writes and reads i l1-l2 20 ma peak clamp current i ccr 7 10 a during eeprom read, v l1/l2 = 2.2v i cct 25 30 a during tamper bit write, v l1/l2 = 2.2v i ccw 150 200 a during eeprom write, v l1/l2 = 3.0 v cnf 5.0 7.0 v 10v through 400 ? , prior to header v mnf 4.0 v 10v through 400 ? , during header v cff 4.0 v 4.5v through 5k ? , prior to header v mff 3.4 v 4.5v through 5k ? , during header dv rcv 1.0 v modulation voltage delta during reception c l 5 pf input capacitance on l1/l2 at 5v, not tested r coil 950 ? maximum coil resistence for coil detection l1 l2 r r + - + - gnd at24rf08 vl1 vl2 v cnf, v cff dv rcv v mnf, v mff
AT24RF08C 16 rf write delay rfid ac specifications at f coil = 125 khz, except where noted. name min typ max units notes f rf 120 125 130 khz coil excitation frequency t bitr 123 128 133 s read bit time, over f rf range t bitw 493 512 531 s write bit time, over f rf range t wd 5.9 11.8 ms write delay, modulation edge to modulation edge t twd 5.6 7.9 11.8 ms tamper bit write delay, modulation edge to modulation edge t modf 16 32 s input modulation fall time, l1 or l2, not tested t modr 16 32 s input modulation rise time, l1 or l2, not tested t twd
AT24RF08C 17 rfid acknowledge timing rfid command/data timing rfid protocol ac specifications at f coil = 125 khz. name min typ max units notes t ack1 256 640 896 s delay from header end to ack. start t ack2 640 896 1024 s delay from header end to ack. end t ack3 32 256 512 s acknowledge pulse width t cmd1 256 768 1024 s delay from data end to cip start t cmd2 32 256 368 s delay from bit time start to modulation change t cmd3 400 512 624 s delay from modulation change to next same change
AT24RF08C 18 timing diagram for serial interface ac specifications serial interface ac specifications c l = 1 ttl gate and 100pf, except as noted. vcc = 2.4v to 5.5v. name min max units notes f scl 100 khz clock (scl) frequency t low 4.7 s clock (scl) pulse low-width t high 4.0 s clock (scl) pulse high-width t i 100 ns noise suppression, not tested t aa 0.1 4.5 s clock low to data out valid t buf 4.7 s bus free before transmission, not tested t hd.sta 4.0 s start hold time t su.sta 4.7 s start set-up time t hd.dat 0sdata in hold time t su.dat 200 ns data in set-up time t r 1.0 s inputs rise time, not tested t f 300 ns inputs fall time, not tested t su.sto 4.7 s stop set-up time t dh 300 ns data out hold time t wr 10 ms write cycle time, eeprom or tamper write
AT24RF08C 19 note: those specifications noted ? not tested ? denote parameters that are characterized and not 100% tested. ordering information serial interface dc specifications name min typ max units notes v cc 2.4 5.5 v operating voltage, v cc pin i ccr 50 100 a at v cc = 5v, f sda = 100 khz, eeprom reads i ccw 0.5 1.0 ma at v cc = 5v, f sda = 100 khz, eeprom writes i sb1 812aat v cc = 5.5v, sda, scl = v ss , rfid idle i sb2 68aat v cc = 3.3v, sda, scl = v ss , rfid idle i lio 0.1 3.0 a prot, sda, scl. v in = v cc or v ss i lwp 20 a input current on wp, at v wp = v dd = 5.5v v il -0.1 v cc x 0.3 v v ih v cc x 0.7 v cc v v ol 0.4 v i ol = 2.1ma c i 6 pf scl, prot, wp. not tested c io 8 pf sda. not tested eeprom memory name min typ max units notes retention 10 years data retention at operating temperature endurance 100,000 cycles per byte package package mark ordering code 8s1 24rf08cn AT24RF08Cn - 10sc
AT24RF08C 20 packaging information .020 (.508) .013 (.330) pin 1 .157 (3.99) .150 (3.81) .244 (6.20) .228 (5.79) .050 (1.27) bsc .196 (4.98) .189 (4.80) .068 (1.73) .053 (1.35) .010 (.254) .004 (.102) 0 8 ref .010 (.254) .007 (.203) .050 (1.27) .016 (.406) 8s1, 8-lead, 0.150" wide, plastic gull wing small outline (jedec soic) dimensions in millimeters and (inches)
? atmel corporation 1999. atmel corporation makes no warranty for the use of its products, other than those expressly contained in the company ? s standard war- ranty which is detailed in atmel ? s terms and conditions located on the company ? s web site. the company assumes no responsibility for any errors which may appear in this document, reserves the right to change devices or specifications detailed herein at any tim e without notice, and does not make any commitment to update the information contained herein. no licenses to patents or other intellectu al prop- erty of atmel are granted by the company in connection with the sale of atmel products, expressly or by implication. atmel ? s products are not authorized for use as critical components in life support devices or systems. atmel headquarters atmel operations corporate headquarters 2325 orchard parkway san jose, ca 95131 tel (408) 441-0311 fax (408) 487-2600 europe atmel u.k., ltd. coliseum business centre riverside way camberley, surrey gu15 3yl england tel (44) 1276-686-677 fax (44) 1276-686-697 asia atmel asia, ltd. room 1219 chinachem golden plaza 77 mody road tsimhatsui east kowloon hong kong tel (852) 2721-9778 fax (852) 2722-1369 japan atmel japan k.k. 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel (81) 3-3523-3551 fax (81) 3-3523-7581 atmel colorado springs 1150 e. cheyenne mtn. blvd. colorado springs, co 80906 tel (719) 576-3300 fax (719) 540-1759 atmel rousset zone industrielle 13106 rousset cedex france tel (33) 4-4253-6000 fax (33) 4-4253-6001 fax-on-demand north america: 1-(800) 292-8635 international: 1-(408) 441-0732 e-mail literature@atmel.com web site http://www.atmel.com bbs 1-(408) 436-4309 printed on recycled paper. 1072e ? 09/99/xm marks bearing ? and/or ? are registered trademarks and trademarks of atmel corporation. terms and product names in this document may be trademarks of others.

▲Up To Search▲

Price & Availability of AT24RF08C

	To Download AT24RF08C Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .